 $ type SYS$HELP:CDD033.RELEASE_NOTES












               VAX Common Data Dictionary Release Notes


                        Order No. AA-GK49B-TE



                           August 1986




          This manual contains the release notes for VAX Common Data
          Dictionary.






          Operating System:  VMS
                             MicroVMS

          Software Version:  VAX CDD V3.3






        digital equipment corporation, maynard, massachusetts

























The information in this document is subject to change
without notice and should not be construed as a
commitment by Digital Equipment Corporation.  Digital
Equipment Corporation assumes no responsibility for
any errors that may appear in this document.

The software described in this document is furnished
under a license and may be used or copied only in
accordance with the terms of such license.

No responsibility is assumed for the use or
reliability of software on equipment that is not
supplied by DIGITAL or its affiliated companies.


Copyright (c) 1981, 1982, 1983, 1984, 1985, 1986 by
Digital Equipment Corporation.  All rights reserved.


The postage paid READER'S COMMENTS form on the last
page of this document requests your critical
evaluation to assist us in preparing future
documentation.

The following are trademarks of Digital Equipment
Corporation:


ACMS           DECUS          UNIBUS
CDD            MicroVAX       VAX
DATATRIEVE     MicroVMS       VAXcluster
DEC            PDP            VAX Information
Architecture
DECgraph       Rdb/ELN        VMS
DECnet         Rdb/VMS        VT
DECslide       TDMS















                                   CONTENTS



CHAPTER 1       Release Notes

        1.1     New Features of CDD Version 3.3  . . . . . . . . . 1-1
        1.1.1     Support of the VAX Language-Sensitive Editor 
                  (LSE)  . . . . . . . . . . . . . . . . . . . . . 1-1
        1.1.2     /DIAGNOSTICS Qualifier for CDDL Command  . . . . 1-2
        1.1.3     DECreporter Support  . . . . . . . . . . . . . . 1-2
        1.2     New CDDL Alternative File Extension in CDD Version 
                3.3  . . . . . . . . . . . . . . . . . . . . . . . 1-3
        1.3     CDD Version 3.3 and VAX/VMS Version 4.0  . . . . . 1-3
        1.4     Installing CDD on a Cluster  . . . . . . . . . . . 1-3
        1.5     Underscore Preceding CDD$TOP . . . . . . . . . . . 1-4
        1.6     Using Multiple Versions of CDD Objects with VAX 
                DATATRIEVE . . . . . . . . . . . . . . . . . . . . 1-4
        1.7     Installing CDD with SYSPRV . . . . . . . . . . . . 1-5
        1.8     Path Names Pointing to Subdictionary Files . . . . 1-5
        1.9     The CDDL ALIGNED Clause  . . . . . . . . . . . . . 1-5
        1.10    DMU Restrictions . . . . . . . . . . . . . . . . . 1-6
        1.10.1    Copying and Renaming a Dictionary Object 
                  Protected by a Password  . . . . . . . . . . . . 1-6
        1.10.2    Using /STAGE with DMU RESTORE  . . . . . . . . . 1-6
        1.10.3    Using a Wildcard with the DELETE/SUBDICTIONARY 
                  Command  . . . . . . . . . . . . . . . . . . . . 1-7

























                                 iii



























How to Use This Manual



1  Purpose of This Manual

1  Purpose of This Manual

This document contains the VAX Common Data Dictionary Release
Notes.  It describes the new features of this release and any
problems you should know about.



2  Intended Audience

2  Intended Audience

This manual is intended for all users of the Common Data
Dictionary.



3  Operating System Information

3  Operating System Information

To verify which versions of your operating system are compatible
with this version of the VAX Common Data Dictionary, check the
                        ___ ______ ________ _____ ______________

most recent copy of the VAX System Software Order Table/Optional
_____ _________ _____

Cross Reference Table, SPD 28.98.xx.



4  Structure

4  Structure

This manual consists of one chapter.  It contains release
information about the VAX Common Data Dictionary.

This manual calls certain VAX Information Architecture products
by their abbreviated names, referring to VAX ACMS software as
ACMS, to VAX DATATRIEVE software as DATATRIEVE, to VAX DBMS
software as DBMS, and to VAX TDMS software as TDMS.



5  Related Manuals

5  Related Manuals

You can find additional information in the following documents:

   ___ ______ ____ __________ ______ _____

o  VAX Common Data Dictionary User's Guide

   ___ ______ ____ __________ _________ _________ ______

o  VAX Common Data Dictionary Utilities Reference Manual




                                  iv
























                                                       Related Manuals


   ___ ______ ____ __________ ____ __________ ________ _________

o  VAX Common Data Dictionary Data Definition Language Reference
   ______

   Manual

   ___ ______ ____ __________ ____________ _____

o  VAX Common Data Dictionary Installation Guide

   _____ __ _______ ______ __________ ___ _____ __________

o  Guide to VAX/VMS System Management and Daily Operations

   _______ ___ __________

o  VAX/VMS DCL Dictionary

   _____ __ _______ ________ ____________

o  Guide to VAX/VMS Software Installation

o  The VAX/VMS Utilities Reference Volume





























                         v














                     Chapter 1

                     Chapter 1

                   Release Notes

                   Release Notes



1.1  New Features of CDD Version 3.3

1.1  New Features of CDD Version 3.3

Version 3.3 contains several new features.



1.1.1  Support of the VAX Language-Sensitive Editor

1.1.1  Support of the VAX Language-Sensitive Editor
       (LSE)

       (LSE)

Version 3.3 of CDD supports the VAX
Language-Sensitive Editor (LSE).  If the VAX
Language-Sensitive Editor is installed on your
system, you can use this feature to help write,
compile, and debug CDDL definitions.  The CDDL
Language-Sensitive Editor provides templates and
menus to walk you through CDDL options and syntax.
It is especially useful for users unfamiliar with
CDDL.

To invoke the Language-Sensitive Editor (also
referred to as LSE), type LSE at the DCL prompt.
The following command, for example, creates a file
ADDRESS.CDDL and displays a CDDL record definition
template to guide you through the process of
describing a CDDL record:


                        1-1



Release Notes

Release Notes
New Features of CDD Version 3.3


$ LSE ADDRESS.CDDL


When LSE compiles your source definition, it expects
a file type of .CDDL.  The CDDL compiler now
recognizes both file types .CDDL and .DDL.



1.1.2  /DIAGNOSTICS Qualifier for CDDL Command

1.1.2  /DIAGNOSTICS Qualifier for CDDL Command

The /DIAGNOSTICS qualifier with the CDDL command
creates a diagnostics file that lists errors
occurring during compilation.  /DIAGNOSTICS is
designed for use from the LSE environment.
/DIAGNOSTICS lists errors in a file that has the
default name of your definition file and the
extension .DIA.  The diagnostic file is reserved for
use by DIGITAL.  LSE uses the diagnostic file to
display diagnostic messages and to position the
cursor on the line and column where a source error
exists.

You cannot use /DIAGNOSTICS with CDDL/RECOMPILE.

                                               ___

For complete information on using LSE, see the VAX
__________________ ______ ______ _____

Language-Sensitive Editor User's Guide.



1.1.3  DECreporter Support

1.1.3  DECreporter Support

If DECreporter is installed on your system, you can
use it to create reports using definitions stored in
the CDD.  You can use either VAX DATATRIEVE or
DECreporter's Report Dictionary Management Utility
to manipulate dictionary objects.  With DATATRIEVE,
DECreporter lets you create reports using VAX
Rdb/VMS and VAX DBMS definitions in the CDD.


                        1-2



                                       Release Notes

                                       Release Notes
                     New Features of CDD Version 3.3


DECreporter supports two ways to define a report:

      o  A menu interface, which helps you navigate
         through the CDD to specify the report
         criteria.

      o  The DECreporter program interface, which
         lets you use DECreporter calls in a command
         file.

To run DECreporter, type REPORT at DCL level.  You
can type HELP REPORT for information on DECreporter
commands and qualifiers.



1.2  New CDDL Alternative File Extension in CDD

1.2  New CDDL Alternative File Extension in CDD
     Version 3.3

     Version 3.3

To support LSE, the CDDL compiler now recognizes the
definition file extension .CDDL as well as .DDL.



1.3  CDD Version 3.3 and VAX/VMS Version 4.0

1.3  CDD Version 3.3 and VAX/VMS Version 4.0

You can install CDD Version 3.3 only on a VAX/VMS
Version 4.0
(MicroVAX/VMS Version 1.0) or higher system.



1.4  Installing CDD on a Cluster

1.4  Installing CDD on a Cluster

If you are using CDD Version 3.3 on a VAX/VMS
Version 4.x cluster, you should install the main
dictionary file (CDD.DIC) on a device that is
accessible to the entire cluster.



                        1-3



Release Notes

Release Notes
Installing CDD on a Cluster


You should also make sure that all system logical
names (including CDD$DICTIONARY, which is used to
identify dictionary files) translate in the same way
on each system in the cluster.  Otherwise, the same
subdictionary directory may point to several
different dictionary files, or you may receive a CDD
error that several subdictionary directories point
to the same subdictionary file.



1.5  Underscore Preceding CDD$TOP

1.5  Underscore Preceding CDD$TOP

With CDD Version 3.1 and later, you can temporarily
define a logical name for CDD$TOP.  (See Section
             ___ ______ ____ __________ ______ _____

8.3.1 of the VAX Common Data Dictionary User's Guide
for a description of the circumstances under which
you might define a logical name for CDD$TOP.)

In path names displayed on the terminal, CDD places
an underscore before CDD$TOP.  The name CDD$TOP is
always translated at least once.  After the final
translation, CDD$TOP will automatically be preceded
by an underscore (_CDD$TOP).

If a logical name translates to an absolute path
name, then CDD$TOP will be translated again.  For
example, CDD$DEFAULT might translate to
CDD$TOP.JONES.  Then CDD$TOP is translated a final
time to _CDD$TOP.



1.6  Using Multiple Versions of CDD Objects with VAX

1.6  Using Multiple Versions of CDD Objects with VAX
     DATATRIEVE

     DATATRIEVE

With CDD Versions 3.0 and later, you can create
multiple versions of dictionary objects.  If you are
using VAX DATATRIEVE, however, you need DATATRIEVE


                        1-4



                                       Release Notes

                                       Release Notes
Using Multiple Versions of CDD Objects with VAX  ...


Version 3.x to access multiple versions of CDD
objects.  Earlier versions of VAX DATATRIEVE do not
support multiple versions of dictionary objects.



1.7  Installing CDD with SYSPRV

1.7  Installing CDD with SYSPRV

If you use the INSTALL utility to install a known
image with the qualifier
/PRIVILEGED=(SYSPRV), you must install the
associated message file with the qualifier _/SHARED.
Otherwise, the image cannot access its own message
file.  For example, if you install DMU with SYSPRV,
you should install DMUEXC.EXE, DMU's message file,
with the qualifier /SHARED.



1.8  Path Names Pointing to Subdictionary Files

1.8  Path Names Pointing to Subdictionary Files

When you move a subdictionary file from one system
to another, make sure that the subdictionary's path
name on the new system is the same as it was on the
old system.  Because both DATATRIEVE and DBMS use
full path names by default to locate data
definitions, changing the path name of a
subdictionary will produce errors when DATATRIEVE or
DBMS tries to access definitions in that
subdictionary.

Currently, CDD does not check to ensure that
subdictionary path names remain unchanged.



1.9  The CDDL ALIGNED Clause

1.9  The CDDL ALIGNED Clause

Be careful when you use the CDDL ALIGNED Clause.


                        1-5



Release Notes

Release Notes
The CDDL ALIGNED Clause


o  You should not use the ALIGNED clause in template
   records.  When CDDL stores the template record,
   the position of an aligned field is fixed within
   the record and is not changed when the record is
   copied into another record definition.
   Therefore, the newly created field may not align
   properly in the new record definition.

o  Records created with the ALIGNED clause using
   previous versions of CDDL may not have aligned
   fields properly.  CDD Version 3.1 corrected this
   alignment problem.  However, if you recompile the
   records using the ALIGNED clause, data already
   stored will no longer match the recompiled data
   definition.




1.10  DMU Restrictions

1.10  DMU Restrictions

You should be aware of several restrictions in the
VAX Common Data Dictionary Data Management Utility
(DMU).



1.10.1  Copying and Renaming a Dictionary Object

1.10.1  Copying and Renaming a Dictionary Object
        Protected by a Password

        Protected by a Password

Cases may occur where you are granted UPDATE and
CONTROL privileges for an object only through a
password.  If this is true, you cannot copy any
version of another object with the same name as the
protected object to the directory containing the
protected object, because DMU COPY provides no way
to specify the protected object's password.




                        1-6



                                       Release Notes

                                       Release Notes
                                    DMU Restrictions


In a case where you are granted the UPDATE privilege
for an object only through a password, you cannot
rename another object as a new version of the
protected object, because DMU RENAME provides no way
to specify the protected object's password.



1.10.2  Using /STAGE with DMU RESTORE

1.10.2  Using /STAGE with DMU RESTORE

If you specify the /STAGE qualifier with the DMU
RESTORE command, all changes remain in virtual
memory until the restoration is completed, to assure
that either all or none of the changes are made.
Therefore, the size of the portion you back up is
limited by the amount of virtual memory.  By
contrast, /NOSTAGE (the default) frees virtual
memory in stages, as each directory is restored.

The DMU BACKUP and RESTORE commands should be used
to back up only portions of the dictionary
hierarchy.  Use the DCL BACKUP command to back up an
entire dictionary file.



1.10.3  Using a Wildcard with the

1.10.3  Using a Wildcard with the
        DELETE/SUBDICTIONARY Command

        DELETE/SUBDICTIONARY Command

With one DELETE/SUBDICTIONARY command you can delete
only 255 or fewer subdictionaries.










                        1-7
